Conversation
added 2 commits
April 21, 2026 13:53
…line The maintainer release path now builds notes from versioned README sections, targets the public GitHub repo from the release manifest, and creates or updates the current GitHub release. The same change also carries the already-verified codex-agent regression coverage that was staged on this sandbox branch. Constraint: Release creation must target recodeee/gitguardex even when origin points at a mirror or worktree-management remote Rejected: Keep gx release calling npm publish directly | still leaves GitHub release notes manual and prone to drift from README history Confidence: high Scope-risk: moderate Reversibility: clean Directive: Keep README release-note sections complete and versioned because gx release now treats them as the source of truth for GitHub release bodies Tested: node --check bin/multiagent-safety.js; node --test test/metadata.test.js; node --test --test-name-pattern "release creates a GitHub release with README-generated notes|release prefers the target repo package manifest when resolving the GitHub repo|release edits an existing GitHub release instead of failing|typo helper maps relaese/realaese to release" test/install.test.js; node --test --test-name-pattern "codex-agent keeps the sandbox when base branch advances without a mergeable remote context|codex-agent surfaces commit-hook failures so unfinished sandboxes are actionable" test/install.test.js; openspec validate auto-release-writer --type change --strict; openspec validate --specs Not-tested: node --test test/install.test.js test/metadata.test.js full command because unrelated setup/doctor areas still time out in the repo baseline
… naming origin/main now exercises the autocommit retry path under agent/planner branch names, so the carried regression assertions needed a narrow follow-up after the finish-flow rebase conflict was resolved. Constraint: The rebase pulled in current workflow-contract changes from main while this branch still carried older agent/codex expectations in test/install.test.js Rejected: Leave the stale assertion in place | it would make the focused codex-agent regression slice fail after the rebase Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep codex-agent branch-name assertions aligned with the current workflow contract when rebasing long-lived release branches Tested: node --test --test-name-pattern "release creates a GitHub release with README-generated notes|release prefers the target repo package manifest when resolving the GitHub repo|release edits an existing GitHub release instead of failing|typo helper maps relaese/realaese to release|codex-agent keeps the sandbox when base branch advances without a mergeable remote context|codex-agent surfaces commit-hook failures so unfinished sandboxes are actionable" test/install.test.js Not-tested: node --test test/metadata.test.js full file after rebase because origin/main currently carries an unrelated doctor-path metadata failure
NagyVikt
added a commit
that referenced
this pull request
Apr 21, 2026
…225) The release branch already merged as PR #224 and its sandbox is gone, so this follow-up updates the existing OpenSpec tasks file with the final merge and cleanup evidence instead of leaving the completion section open. Constraint: The original finish run completed the merge but ended with a stale remote-ref deletion error after GitHub had already removed the merged branch Rejected: Leave the completion checklist open and rely only on chat handoff | the repo contract expects the OpenSpec change record to carry the merge and cleanup evidence Confidence: high Scope-risk: narrow Reversibility: clean Directive: When a finish flow merges but cleanup evidence is not recorded in the change bundle, add a narrow follow-up to the existing tasks file instead of creating a new behavior change Tested: openspec validate auto-release-writer --type change --strict; git diff --check Not-tested: Runtime/test suites, because this is a documentation-only completion-evidence update Co-authored-by: NagyVikt <nagy.viktordp@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated by scripts/agent-branch-finish.sh (PR flow).